Methods and Devices for Defending a 3G Wireless Network Against Malicious Attacks

ABSTRACT

Wireless state information collected or inferred from a 3G wireless network is used to detect and prevent malicious attacks against the network.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 11/303,915, filed on Dec. 19, 2005.

BACKGROUND OF THE INVENTION

The frequency and magnitude of malicious attacks against wireless networks have been steadily increasing.

A large variety of solutions have been proposed to counter malicious attacks against communication networks. While these schemes may mitigate the threat of attacks against wireline networks they are inadequate for wireless networks.

For example, in a wireline Denial of Service (DoS) attack it takes a long period of time, relatively speaking, for a server to be disabled because such machines have a larger processing capacity than a wireless endpoint (mobile) which has limited processing and battery lifetime. In addition, a wireless link is severely bandwidth-constrained when compared to a wireline network. Thus, if traffic from an attack reaches a mobile, the attack has already succeeded in wasting critical resources of the wireless link, the wireless infrastructure, and the battery power of the mobile. This is in contrast to typical wireline DoS attacks that must overwhelm processing resources at a server in order to succeed.

There are numerous types of attacks that are attempted against wireless networks, two of which are signaling type attacks and battery (i.e., sleep deprivation) attacks. Co-pending U.S. patent application Ser. Nos. 11/094,416 and 11/236,735, incorporated herein in full as if set forth in full herein discuss such attacks and propose specific techniques for defending against such attacks.

However, attacks against a 3G wireless network are not limited to just signaling and battery attacks.

It is desirable, therefore, to provide methods and devices for defending many types of 3G wireless networks against numerous types of attacks.

SUMMARY OF THE INVENTION

The present inventors have recognized that attacks against 3G wireless networks may be prevented, or substantially reduced, by making use of collected or inferred wireless state information.

More specifically, one embodiment (i.e., example) of the present invention provides for the detection of an attack against a 3G wireless network by obtaining wireless state information and comparing the obtained information to a profile to determine whether an attack is directed at an element in the network.

By using wireless state information the present inventors believe attacks can be more readily detected and prevented.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an example of an architecture for defending a 3G wireless network against attacks according to one embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION, WITH EXAMPLES

To defend mobile devices in 3G wireless networks against numerous types of attacks, the present invention provides a novel architecture referred to as an architecture for Wireless Attack Resistance (AWARE).

FIG. 1 depicts one example of an AWARE architecture according to one embodiment of the invention.

In one embodiment of the present invention, an AWARE architecture (e.g., enabled device) 100 may comprise a learning database or profiler 101, and a detection engine or detector 102. The profiler 101 may be operable to collect wireless state information from the different elements of the wireless infrastructure 1 (e.g., network) including a base station (BS) 103, radio network controller (RNC) 104 and Packet Data Service Node PDSN, 105. In an alternative embodiment of the invention, the AWARE enabled device 100 may infer state information from its knowledge of the wireless network 1 when collection is not possible.

The profiler 101 is operable to capture and store information about a user 200, typically during a pre-processing step, in order to generate a traffic profile for a given user under normal (i.e., non-attack) conditions using, for example one or more statistical measures. In a further embodiment of the invention, after an initial profile is created the profiler 101 may update the profile regularly based on changes to a user's behavior. Information used in building the profile includes, but is not limited to, packet arrival times, IP addresses and port numbers of source(s), and destination(s). It should be understood that the profiler 101 may comprise one or more databases. These databases may communicate with other user databases and profilers for cross-mobile, cross RNC, or cross PDSN correlations. For example, data from multiple databases associated with one or more PDSNs may be aggregated and analyzed for similarities, for example. A similarity may indicate the onset or presence of an attack that spans multiple PDSNs.

One novel aspect of the profiling mechanisms provided by the present invention is the ability to correlate user, application, as well as server related profiles. By user profile, we refer to the statistics for an individual user. This division can be further categorized by individual application. For instance, web surfing is the most frequently used service by most users. Similarly, a video-on-demand server may use RTP packets to broadcast video to users. Statistics on an individual web server basis or any IP source an also be compiled by logging the arrival of HTTP/RTP packets.

To enable scalability, the profiler 101 may be operable to aggregate profiles across users with similar behaviors using, for example, the same metric. Aggregation allows profiles to be stored in a scalable manner so that it may, for example, be more easily correlated later on. For example, current traffic may be compared to an aggregated profile to detect inconsistencies. Aggregated profiles may also be maintained for popular servers and applications. The flexibility of using different classification approaches allows a more comprehensive and accurate characterization of what is considered as normal traffic.

Turning now to the detector 102, it is operable to detect a 3G wireless attack using one or more detection heuristics.

In slightly more detail, one example of a signaling cost which may be used is the signaling cost as traffic traverses through the wireless network 1. Malicious traffic may be identified because it introduces excessive signaling cost. The cost of signaling can be obtained in various ways depending on the cooperation that can be obtained from elements within the wireless network 1.

In one embodiment of the present invention, the detector 102 may be operable to compare a stored non-attack or normal profile with current traffic conditions to determine whether current traffic for a user or set of users 200 violates the normal profile.

Once an attack is detected and the attacker identified, the AWARE enabled device 100 may block all future traffic from the suspected attacker by, for example, reconfiguring or configuring the firewall 106 (e.g., setting rules in the firewall).

As mentioned before, AWARE enabled devices provided by the present invention collect wireless specific state information including the setup and release of wireless data channels, and the time that a mobile is active. The inventors know of no other device as of this date that collects wireless state information and uses it to detect 3G wireless attacks in a manner akin to the present invention.

In further embodiments of the present invention, the AWARE-enabled device 100 may be operable to maintain information at different levels of granularity (for the same measurement parameter). Said another way, for the same measurement parameter, different aggregation levels may be used. For example, a per-mobile, per-RNC, per-BS, per-PDSN or per-external-source basis. This allows the detection heuristic to find anomalies at multiple levels, preventing an attacker from spreading malicious traffic across different RNCs or launching an attack that doesn't limit itself to a particular BS,

In accordance with the present invention, the location of an AWARE-enabled device may be varied.

For example, an AWARE-enabled device may be co-located with a firewall 106 of a wireless service provider. If such a design is chosen then it may not be necessarily assumed that any other part of the wireless network 1 has knowledge of the presence of the AWARE-enabled device 100 or interacts with the AWARE-enabled device 100.

In a further embodiment of the present invention, the profiler 101 of such a co-located AWARE-enabled device 100 may use IP layer information, such as packet arrivals and information from IP/TCP and application layer headers, to build profiles. This assumes that the AWARE-enabled device 100 can look inside a packet. If an IPsec (tunnel mode) has been enabled, the AWARE-enabled device 100 may be co-located with an IPsec gateway in the domain so as to be able to decrypt and inspect package headers and payloads.

In a “least-invasive” design, the AWARE-enabled device 100 looks at IP packets that are passed on from the firewall 106 before they reach the PDSN 105. All of the necessary information is contained in the TCP and IP headers and the payload itself. Information needed by the profiler 101 to build a profile can be extracted from the above headers and payload.

In a AWARE-enabled device is not co-located with an IPsec gateway, there needs to be a so-called security association with the gateway so it can decrypt and process ESP-encapsulated packets in a tunnel mode.

If an AWARE-enabled device is not co-located with a firewall, an interface may be used to communicate with most commercial firewalls, such as Checkpoint's Firewall-1, so that an AWARE-enabled device may configure the firewall's filters, etc.

In an alternative embodiment of the present invention, an AWARE-enabled device 100 may operate between a PDSN 105 and an RNC 104. In such a design, the device may interact with the PDSN 105 to obtain information as to how packets are distributed to different RNC's.

In addition, when an AWARE-enabled device operates between a PDSN and RNC more user-specific state information may be gathered. This provides finer grain information, such as: the number of signaling events for a FCH & SCH setup/release, the timestamp(s) of signaling messages, and power control information via a base station that estimates mobile power consumption. An AWARE-enabled device may also be able to obtain mobility related information because a mobile may cross over from one RNC to another. The impact of mobility information on the detection heuristic is worth analyzing, because highly mobile end-users can contributed significantly to the load of an network. Launching a wireless DoS attack, for example, against highly mobile users requires additional tasks, such as more frequency paging, that can add substantially to processing overhead. Also, a mobile may initiate a PPP connection with the PDSN before initiating a transfer. An AWARE-enabled device may also query the PDSN to obtain a PPP state history.

An AWARE-enabled device can also query an RNC for channel setup events as well as power control messages that are sent to the mobile to indicate at what power the mobile should transmit the data.

AWARE-compatible interfaces may also be provided by the present invention. In further embodiments of the present invention, AWARE-compatible interfaces are provided to allow an AWARE-enabled device, for example, to query wireless user/mobile state(s). Such an interface may also allow an AWARE-enabled device (or devices) to communicate in a secure manner with elements of a wireless network in order to obtain mobile/user-specific information.

It should be understood that the methods of the present invention, the AWARE-enabled devices, interfaces, and any subcomponents (e.g., learning database, profiler, detector, etc.) may be realized in hardware, software, firmware or some combination of the three. For example, one or more programmable or programmed controllers, processors, or computer readable mediums, separately or in combination, may be operable to store one or more instructions, programs or code (and data) that, in turn, is operable to carry out the features and functions of the present invention described above and in the claims that follow. 

We claim:
 1. A method for detecting an attack against a wireless network comprising: Generating a profile based on non-attack, wireless traffic conditions; obtaining wireless state information comprising wireless data channel set-up and release information and application based information; and comparing the obtained information to the profile to determine whether an attack is directed at an element in the wireless network.
 2. The method as in claim 1 further comprising preventing malicious traffic intended for a mobile device in the network from reaching the device when the comparison indicates an attack.
 3. The method as in claim 1 wherein the state information is collected from one or more network elements in the network.
 4. The method as in claim 1 wherein the state information is inferred from knowledge of the network.
 5. A device for detecting an attack against a wireless network operable to: generate a profile based on non-attack, wireless traffic conditions; obtain wireless state information comprising wireless data channel set-up and release information and application based information; and compare the obtained information to the profile to determine whether an attack is directed at an element in the wireless network.
 6. The device as in claim 5 further operable to prevent malicious traffic intended for a mobile device in the network from reaching the device when the comparison indicates an attack.
 7. The device as in claim 5 wherein the device is further operable to collect the state information from one or more elements in the network.
 8. The device as in claim 5 wherein the device is further operable to infer state information from knowledge of the network.
 9. The method as in claim 1 wherein the wireless state information further comprises time-based mobility activity information.
 10. The method as in claim 1 wherein the wireless state information further comprises IP layer information.
 11. The method as in claim 10 wherein the IP layer information comprises packet arrivals and information from IP/TCP application layer headers.
 12. The device as in claim 5 wherein the wireless state information further comprises time-based mobility activity information.
 13. The device as in claim 5 wherein the wireless state information further comprises IP layer information.
 14. The device as in claim 13 wherein the IP layer information comprises packet arrivals and information from IP/TCP application layer headers. 